旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � 悶 悶 悶 敏� � 悶 悶 � � 悶 悶� 悶 � 붜 � � 처 납 � � 납 냄 � � � � � 납 � Version 3.10 붜 � � 납 읏 � 납 납 납 � � 납 � � 읏 � (C)1996 Fe-line Software 붜 � � 廟 잎 � 잎 잎 잎 � � 잎 � � 잎 � 붜 突袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴송 賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽賽� FastLog/IEMSI PEX for ProBoard BBS Version 2.1x 18th April 1996 FastLog/IEMSI was written and Designed by Faye Pearson. FastLog/IEMSI Documention was written by Sarah Pearson. How to use FastLog/IEMSI v3.10 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � FastLog/IEMSI : Introduction to FastLog/IEMSI (C)1996 Fe-line Software � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� FastLog/IEMSI is a ProBoard 2.1x PEX that allows you to do a number of things when a User logs in. FastLog v1.00 was first developed after receiving numerous requests from our Users that they missed the shortcut ! option of Wildcat* before their Username when logging into our BBS. (* Wildcat is a trademark of Mustang Software) As the early versions of FastLog were developed, we were asked about incorporating IEMSI support into FastLog as the only other ProBoard IEMSI PEX available at that time was not so good. FastLog/IEMSI was developed and has grown to include many new features and now has a very healthy Userbase. v3.00 of FastLog/IEMSI is the biggest upgrade we have made to the package and we thought the changes warranted a version number 3.00 :-) v3.10 now has the facility to display scrolling Help Text for new users and/or display a scrolling welcome message to all users. 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � FastLog/IEMSI : About (C)1996 Fe-line Software � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� One of the biggest changes since v2.30 is the removal of the @pIEMSI ...@ Language file amendments which were needed for previous versions of FastLog/IEMSI. FastLog/IEMSI now controls the whole New User Login procedure. The result is an exact replica of the Internal ProBoard New User procedure, but with some fixes. Because we have re-written the IEMSI Handling routines, IEMSI logins are now more or less instant. Non-IEMSI Users still see no loss in speed when logging onto your BBS. ASCII Support is also provided and FastLog/IEMSI will work just as well. You can still use your existing ASCII screens. When FastLog/IEMSI v3.10 is run for the first time, a local only screen is displayed that informs the Sysop that an index file is being created to make the checking of duplicate Passwords, Date of Birth and Voice/Data Telephone numbers much quicker. This screen is only shown once. The index file is called SECURITY.IDX and is located in the ProBoard MessageBase Directory. Below is a detailed list of what FastLog/IEMSI is capable of. � IEMSI : IEMSI is a protocol that allows your Users to log into your BBS without having to type in their name and password. IEMSI can also provide the BBS Software with information that can be used to automate several processes. MAIL : Whether the User would like to check for new mail. With the ASK pex included in this archive, the User will be shown any new mail automatically if their IEMSI handshake requests MAIL. FILE : Whether the User would like to check for new files. With the ASK pex included in this archive, the User will be shown any new files automatically if their IEMSI handshake requests FILE. NEWS : Whether the User would like to check for news. With the ASK pex included in this archive, the User will be shown any news automatically if their IEMSI handshake requests NEWS. HUSH : Whether the User would like to be available for Chat. With the BUSY pex included in this archive, the User will be automatically made BUSY if their IEMSI handshake requests HUSH. CHAT : The Users system has facilities for split screen chat. A pex could be written to detect this and enable an IEMSI Chat Request. FSED : Whether the User requests to use a Full Screen Editor. CLEAR : Whether the User requests Clear Screen to be enabled. HOT : Whether the User wants Hot Keys enabled for their call. MORE : Whether the User wants the More prompt enabled for their call. ASCII8 : Whether the Users System supports the IBM Extended character set. TERMINAL EMULATION : Whether the Users system supports Avatar, AVT/0+, ANSI or nothing. How many screen lines are usable on the Users screen. The width of the Users screen. PROTOCOLS : IEMSI provides a list of Protocols which the Users system is compatible with. FastLog/IEMSI matches the best compatible Protocols and sets the User Record accordingly. IEMSI also contains the Users Name, Password, Location, Voice and Data numbers, their Alias and what Software package they are using. IEMSI also tells the Users system some things about the BBS they are calling. The name of the BBS, local time and date to the BBS and other things. IEMSI logins are logged to the node directory and the level of logging is determined by the LogLevel option in ProCfg. The reason we do not want to just read the Users current log level from his/her User Record is because you may want to log the IEMSI session information but not any other information that ProBoard logs itself. � Scrolling Welcome Text on the Login Screen. To help make you login ANSI look distinctive you can add a line of scrolling text. You can position this text anywhere on the screen, but only horizontal. Open LOGIN.INI and edit the following options : ScrollText = "" ScrollCol = 0b [Default is 0b Cyan on Black] ScrollX = X-coordinate [Default is 20] ScrollY = Y-coordinate [Default is 1] ScrollLen = Length of scroll window. [Default is 40] If ScrollText is remarked out (prefixed with a ; in LOGIN.INI) then ScrollCol, ScrollX, ScrollY and ScrollLen have no effect. � Toggle whether you want Full IEMSI logging or just the name of the IEMSI software used by the User is logged. Open LOGON.INI and edit the FullIEMSILog = option. YES will log all the IEMSI information into the current nodes PROBOARD.LOG file. NO will only log the IEMSI Users software and the fact that they logged in with FastLog/IEMSI. � New User IEMSI Questions. FastLog/IEMSI uses its own New User Questions that look and act exactly the same as the Internal ProBoard New User Questions. Most questions are fully configurable from within ProCfg and only those that have been enabled will be asked. All questions are asked in the New Users chosen language. There is no need for additional .INI files for each Language as the ProBoard .PBL files are used. If only one language is enabled in ProCfg/Language Editor, then the New User is not asked for their preferred language. IEMSI New User support is built in so IEMSI New Users will find some of the questions answered automatically, using information contained in their IEMSI handshake packet. Now there is no need to edit your Language files, IEMSI New User Support is provided directly from _LOGIN.PEX. � Check the Users name and if their first name is 1 character long or the second character contains either .,- then optionally define if the Username is refused. Open LOGIN.INI and edit the AllowInitials = option. Yes will mean that the User can log in with a name like S. Pearson or F Pearson. � The following .A??, PEX and Q-A files are hardcoded to be displayed if they exist. NEWUSER.A?? NEWUSER1.A?? NEWUSER2.A?? NEWUSER.PEX NEWUSER1.PEX NEWUSER2.PEX NEWUSER.Q-A TRASHCAN.A?? These files are hardcoded and display and work in the same way that the standard ProBoard Login procedure does. � The ANSI/AVATAR/AVTPLUS New User Questions default to the detected terminal emulation of the New User. Pressing through these questions will in most cases give the right results. eg, The User logs in with ANSI but not AVATAR capabilities. Would you like to use ANSI? [Y/n] Would you like to use AVATAR? [y/N] But if they log in with ASCII then : Would you like to use ANSI? [y/N] � Added a New User Question to ask for their Default Protocol when completing the New User Login. Versions of ProBoard prior to 2.15 did not directly support the Default Protocol option. Some PEXs provided this facility (like ATRAN) so you can force FastLog/IEMSI to ask the question in this case. It will be asked automatically when using ProBoard 2.15 or greater. ProBoard does not ask the New User to choose their default protocol when logging in for the first time. We have added the question "Available Protocols Z Zmodem Y Ymodem etc Select Protocol :" to be asked immediately after the "What is your Screenlength" question. If the New User presses without making a choice, then the "No Default Protocol" choice is assumed. This question will only be asked if ProBoard is version 2.15 or greater or you specifically request it in LOGIN.INI. If you wish to specify in LOGIN.INI that this question will be asked in ProBoard v2.10-2.12 then open LOGIN.INI and edit the AskProtocol = option to YES. 2.15 has better handling of the Default Protocol and has new Language prompts and Menu Functions. This question is asked using the .PBL files so will be multi-lingual as are all FastLog/IEMSI prompts without having to resort to complicated .INI files. � Define whether or not to enable all QWK or New Mail Scan areas for New Users. This option allows you to automtically turn ON all Message Areas for Personal Mail Scan and/or QWK Combined Mail Boards. Open LOGIN.INI and edit the EnableAllQWK = and EnableAllNew = options. For greater control you can use our SetArea pex which allows you to make sure certain areas are always scanned for mail. You can freq it from one of the node numbers or our WWW/FTP sites at the end of this document. � Logins are now possible when only the CRC is stored for the password. If a User's record has no visible password entry, and only the CRC of their password is stored, FastLog/IEMSI will allow that User to log in. � Save the Password in the Password field if a Users Record only contains the Password CRC. If you have converted a previous BBS User Record file to ProBoard, you may fimd that the password field in the User Record is blank. The password is stored in a CRC. You can optionally convert and then save the CRC into a readable password in the Password field. The CRC value is left intact. Open LOGIN.INI and edit the line SavePassword = option to = YES (make sure you uncomment the line). � Post a Sysop definable message to a New User for reading on their 1st call. The message can be posted to a message area that is setup as both Private and Public by setting the NewPvtMsg option to YES. Open LOGIN.INI and edit the following lines : NewPostMsg = NewMsgArea = NewMsgFName = NewMsgSubj = NewPvtMsg = NewSysopName = If you use our AUTOPOST PEX then please delete it and the autopost.ini file and edit the LOGIN.INI file accordingly. � Post a message to the Sysop with useful New User Information. Open LOGIN.INI and edit the following line : SysopPost = � Position the Login Langauge prompts anywhere you want. The benefit of this options is to allow you to position the Login Prompts so that you can have some nice ANSI/AVATAR effects. ASCII users can only benefit from the X coordinate. The coordinates start from the top-left (1,1). Open LOGON.INI and edit the following options. [All of these X and Y co-ordinates are optional] UserNameX = X position of the Enter Name Prompt UserNameY = Y position of the Enter Name Prompt UserPassY = X position of the Enter Password Prompt UserPassY = Y position of the Enter Password Prompt IsNewX = X position of the Are you a New User Prompt IsNewY = Y position of the Are you a New User Prompt ScanningX = X position of the Scanning Userbase Prompt ScanningY = Y position of the Scanning Userbase Prompt BadPassX = X position of the Illegal Password Prompt BadPassY = Y position of the Illegal Password Prompt NoOneWdX = X position of the No One Word Names Prompt NoOneWdY = Y position of the No One Word Names Prompt LockedX = X position of the You are Locked out of the System prompt. LockedY = Y position of the You are Locked out of the System prompt. NoAccessX = X position of the You are not allowed to access this node prompt. NoAccessY = Y position of the You are not allowed to access this node prompt. TrashNameX = X position of the Illegal Name prompt. TrashNameY = Y position of the Illegal Name prompt. � Displays BEFOREPW.A?? and AFTERPW.A?? files. These two optional files are displayed before and after a User enters their password. They work in the same manner as the Standard ProBoard login procedure. � Duplicate Password, Date of Birth and Telephone Number Checking. FastLog/IEMSI can check the New Users Password, Date of Birth and Voice/Data numbers against the User Base and if any duplicates are found, a message is posted to the Sysop. The search is very quick even on very large UserBases. There is no additional installation requirements for this part of FastLog/IEMSI. � Force ClearScreen, Hotkeys or More Prompt ON or OFF for New Users. We think these options are quite a necessity for a good looking BBS setup, but some New Users do not know what they mean. In LOGIN.INI you can force any of these options ON or OFF and the New User will not be asked the Question relating to what has been forced on. Commenting OUT the line will ask the User the question. Examples. Clear = YES will turn ClearScreen ON for the New User and they will not be asked the "Do you want to use ClearScreen codes?" Question. Clear = NO will turn ClearScreen OFF for the New User and they will not be asked the "Do you want to use ClearScreen codes?" Question. ; Clear = will ask the "Do you want to use ClearScreen codes?" Question to the New User. The same rule for ON/OFF/; applies to More = and Hotkeys =. � Force a New User into ANSI. This option will allow you to stop New Users using ASCII on your BBS. Open LOGIN.INI and edit the ForceANSI = options to YES to force ANSI on. You can comment out this line or put a ; (comment out) in front of the line to ignore this option. If you do use this option to force ANSI on, and effectively stop ASCII New Users, then you can display an optional .ASC screen to the New User upon login. The file FORCEANS.ASC will be displayed as soon as the User answers YES to "Are you a New User" prompt. NOTE that FORCEANS.ASC is optional. � Fixed ProBoard problem of displaying in ANSI when the New User answered NO to the "Do you want to use ANSI" "AVATAR" "AVATAR+" questions. The Users settings are changed *immediately* after the questions are asked. ProBoard does not seem to set the Users Record to TTY until their next call. This is a problem if the User can't display ANSI. � If the New User doesn't select ANSI/AVATAR/AVATAR+ when filling out the New User Questions, then FastLog/Log will NOT ask the "Do you want to use the Fullscreen Editor?" question. It seems very silly to ask this question when the User has chosen TTY. � If there is a in the buffer after the New User answers YES to I am a New User, then the "Available Language" Question is NOT answered automatically to the default. � Set New User Expiry Level, Expiry Flags and Number of Days for Expiry. Open LOGIN.INI and edit ExpireLevel =, ExpireFlagsOn =, ExpireFlagsOff = and ExpireDays = to the required values. � Set the number of lines in the "What is your mailing address?" prompt that have to contain some text input. The minimum length for "some text" is 5 characters. Open LOGIN.INI and edit the BlankAddress = option. 0 or commented out = all 3 lines can be left blank. 1 = Only the first line must contain some text 2 = Only the first and Second line must contain some text 3 = All 3 lines must contain some text. If they enter something less than 5 characters, they are prompted again to enter their Address on that line. � Allows an existing User to use a sysop-definable character in front of their User Name thus allowing the User to get more quickly to the part of the BBS that they want to use. For example, go directly to Offline Mail Doors without going through the menus or skip ANSI screens and go directly to a menu. This could be a quite powerful function. In our example, * before the User's name will go directly to the BlueWave Offline Mail Door. *Sarah Pearson You will need to open LOGIN.INI and edit/add the FlagChar* = option. After the = put the flag you wish to use. Here we use Flag 2. Make sure you use a flag which isn't already being used. You can set up other shortcuts (or change the * to something else) by editing or adding extra FlagChar .INI options and then creating new TOP menu functions. For this example to perform, you need to put an entry into your TOP menu, for ProBoard to act upon. �袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴�[ TOP ]袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴� � 0 1 2 3 4 5 6 7 � � 12345678901234567890123456789012345678901234567890123456789012345678901234 � � ;같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같같� � � � � Color : Bright Cyan on Black Example Text � � � � HotKey : � � Function : 7 - Shell � � Data : *Z*SBWDOOR.BAT /T*# /S*M � � � � Min.Level: 10 Nodes: All nodes � � Max.Level: 0 � � Flags : ---------------------------2---- � � Min. Age : 0 Password required: No � � Max. Age : 0 Password: � � Sex : Don't Care � � Time Left: 0 旼RIP컴컴컴컴컴컴컴커 � � Time Onl.: 0 � Show remote : No � � � Timeframe: Fully enabled � Show local : Yes � � � Min.Speed: 0 � Reset screen: Yes � � � Max.Speed: 0 읕컴컴컴컴컴컴컴컴컴� � � � 훤袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴袴暠 In local mode, typing * will display the Sysop Name and then go directly to Bluewave. Pressing alone will display the Sysop Name and then go into the BBS, just as the Standard ProBoard Login procedure does. (Assuming you have Allow Quick Login Enabled in ProCfg/Options/Security). � Allow an existing User to put their password on the same line as their username. eg, Sarah Pearson Feline The User can also use the prefix character as well. eg, *Sarah Pearson Feline This makes a non-IEMSI login potentially almost as fast as an IEMSI login and also simplifies User's login scripts. � Restrict Nodes by Modem Speed. You can restrict nodes to a certain modem speed (eg, 14k4) so that only those Users with a high speed modem can access the node. Open LOGIN.INI and edit the MinSpeedNode? = ???? line. ? is the Node Number and ???? is the baud rate. If a User attempts to login into a node with a Modem Speed restriction and they are too slow, then a message is posted to the User and to the Sysop and the file specified in the LOGIN.INI RejectUser = option is displayed. Open LOGIN.INI and edit the following options to the show the files and the message info you would prefer. RejectUser = MsgArea = MsgFname = MsgSubj = � Restrict Nodes by Security Level. You can restrict nodes to a certain security level. (eg, 60) so that only Users with a high enough security level can access the node. Open LOGIN.INI and edit the MinSecNode? = ?? line. ? is the Node Number and ?? is the security level. If a user does login without a high enough security level, the file specified in the LOGIN.INI RejectUser = entry is displayed. A message is also sent to the User and the Sysop ProBoard has this option also, and is also capable of displaying an .A?? but doesn't have the option of posting messages. � Allow New Users to log onto a node when MinSecNode is set to a security level higher than that assigned to New Users. eg, New Users are given a level of 10 and MinSecNode1 = 50 The new user is not allowed to log onto Node 2 but with AllowNewUsers = YES in the LOGIN.INI file, they are allowed too. Open LOGIN.INI and edit the AllowNewUsers = ??? entry. ??? can be either YES or NO. This allows you to keep your node security levels, but not lose a New User. � Still use your @a...@ and @p....@ Langauge Prompts. If you use a PEX in your "Please enter your password " language prompt, then you can still use it. See the ProBoard Manual for information on how to use the @a...@ and @p...@ Langauge Prompts. � Uses the Users selected Langauge prompt. No need to use multiple .INI files for each language you require. � All New User Information and Flags are read directly from CONFIG.PRO. � The ProBoard TRASHCAN.CTL is implemented. The TRASHCAN.CTL is a file that the Standard ProBoard login procedure uses to check if a User Name is invalid. See the ProBoard Manual for further Information on TRASHCAN.CTL. � MultiTasker Aware. FastLog/IEMSI can detect and support the following multitaskers : Windows 3.x, Windows 95 and DesqView and OS/2 � Other Useful FastLog/IEMSI Options. � If a user doesn't login successfuly, providing the Procfg/Security/Write Password Failures option is enabled, a message is posted to the Sysop, User and to the log file for that node. Whatever the setting, the User is asked if they would like to leave a message to the Sysop. � If a GUEST User logins then, FastLog/IEMSI will not ask for the password if the password field in the User Record is blank. [They do not have to be called GUEST, just have the GUEST Flag] � If a user is locked out of the System, then the ProBoard Langauge prompt telling them "You are locked out of the system!" is displayed and also an explanation can be displayed by using %a in the prompt. The Comment field in the User's Record is where you store the reason. Edit the language prompt for "You are locked out of the System" Prompt 23 to include an extra line and add something similar to : You are locked out of the System Reason : %a � Procfg's Allow Quick Logon function for Sysop is fully supported in either YES or NO mode. As is the Default Language. � All flags that are defined in LOGIN.INI are cleared for that user on their next call. Unless of course they use the same options again on their next call. � You can use the @a.....@ command (in your prompts) as specified in the ProBoard manual to display an ANSI/ASCII file to the user during login. � All password failures are logged in the correct node directory log file. � Minimum Password length is taken from ProCfg. ASK.PEX is included in this archive to make IEMSI Mail, File and News requests automated. ASK *can* also be run without IEMSI, in which case the caller is prompted if they would like to check for new mail, files and news depending on the parameters passed. The Paramters for ASK are : M for mail F for Files N for News For example, KEY : CTRL-A (automatic or select a menu key) FUNCTION : 60 Run SDK file DATA : ASK MFN This will prompt the User if they would like to check for new personal mail, new files and any news since their last login. If the User has logged on with IEMSI and has MAIL in their handshake packet, then the mail check is answered automatically, similarily with FILE and NEWS. If a caller only has MAIL in their IEMSI Handshake packet, and you have used the above example paramters, then they will be *asked* if they want to check for new files and news, just as the non-IEMSI caller would be. The use of ASK.PEX is optional. ASK.PEX is also DOING Compatible. See the enclosed file DOING.TXT for information on what DOING is about. BUSY.PEX BUSY will make the current node unavilable for multinode chat. This pex will work automatically if the User logs in with IEMSI and has HUSH in their IEMSI handshake packet. BUSY can also be run without IEMSI, maybe as a menu option. BUSY ON will make the current node unavailable. BUSY OFF will make the current node available. BUSY ASK will ask the caller if they wish to be available for multinode chat. BUSY IEMSI will set the busy indicator for multi-node chat if the IEMSI handshake packet contains HUSH. For example, KEY : X (or whatever key you would like) FUNCTION : 60 Run SDK file DATA : BUSY ASK This will ask the current caller if they would like to be available for multiniode chat. The use of BUSY.PEX is optional. 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� � FastLog/IEMSI : Registration (C)1995/96 Fe-line Software � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴� This version of FASTLOG/IEMSI is ShareWare. You can use FASTLOG in [EVALUATION] mode for a period of 30 days. If you wish to continue using FASTLOG after the 30 days then you must register. See REGISTER.EUR for information on how to register in Europe and REGISTER.USA for information on registering in the USA. This PEX is supplied "as is" and we will not be held responsible for any damage caused by this PEX. It works on our BBS ok, so that is the only guarantee given :-) -- Sarah & Faye, sysops@fe-line.demon.co.uk Home of Fe-line Software http://www.win-uk.net/~fe-line ftp://ftp.win-uk.net/pub/users/fe-line ProBoard *UK* Registration and Support Site ProBoard Beta Team SCiNET European Zone Coordinator PSN *UK* Regional Coordinator 旼컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴커 � We can be reached on the following Node Numbers. � � (2:254/278 Fido / 311:21/0 PSN / 173:902/300 DqP-Net / 752:752/0 SCiNET) � � sysops@fe-line.demon.co.uk / Internet � 읕컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴컴켸